<?xml version="1.0" encoding="utf-8"?>
<guidanceItem id="" type="testcase" title="" topic="" category="" priority="" status="" author=";" ruleType="" technology="" source="" date="6/14/2006" xmlns="urn:microsoft:guidanceexplorer:guidanceItem">
  <content>
  <![CDATA[
<H1 class=section>Test Cases</H1>
<P><STRONG>Applies to:</STRONG></P>
<UL>
<LI>Does the list contain specific technology and version (eg. ASP.NET 2.0)?</LI></UL>

<P><STRONG>Objectives:</STRONG></P>
<UL>
<LI>Are the most important learnings from the document extracted into the objectives?</LI>
<LI>Is each objective expressed as a specific task?</LI>
<LI>Is the objectives list short enough that it can be easily scanned and understood?</LI></UL>

<P><STRONG>Overview:</STRONG></P>
<UL>
<LI>Does the overview provide enough background information to understand why it is necessary to take the steps?</LI>
<LI>Does the overview provide enough information that the module can stand alone? </LI></UL>

<P><STRONG>Summary of Steps:</STRONG></P>
<UL>
<LI>Is there a numbered list the explains each step in the document?</LI>
<LI>Do the steps match to the document sections exactly?</LI></UL>

<P><STRONG>&lt;&lt;Step N&gt;&gt;:</STRONG></P>
<UL>
<LI>Does each step explain what to do, why it is important and then how to take action?</LI>
<LI>If there is a decision point is it called out with an explicit ‘if…’ condition? </LI>
<LI>Is the document capable of standing alone without requiring the user to search elsewhere to complete the testing procedure?</LI>
<LI>Where appropriate, are there code or configuration file examples?</LI></UL>

<P><STRONG>Repro Example:</STRONG></P>
<UL>
<LI>Is there a <STRONG>Flawed Code</STRONG> section that contains an example of what the flaw looks like in application code or configuration files?</LI>
<LI>Is there a <STRONG>Test Example</STRONG> section that shows what a tester would have to do to expose the flaw?</LI>
<LI>Does the <STRONG>Test Example</STRONG> contain real user input or steps that would result in a bug in the real world?</LI></UL>

<P><STRONG>Tools Support:</STRONG></P>
<UL>
<LI>Are all the relevant tools useful for test case listed?</LI></UL>

<P><STRONG>Additional Resources:</STRONG></P>
<UL>
<LI>Are the links from trusted sites?</LI>
<LI>Are the links correct in context of the test case?</LI></UL>

<P><STRONG>Related Items:</STRONG></P>
<UL>
<LI>Are the correct items linked in context of the test case?</LI></UL>

<H1 class=section>Additional Tests to Consider When Writing a Test Case</H1></H3>
<P><STRONG>Checkpoint:</STRONG></P>
<UL>
<LI>Is title in the form of "How to Test For xxxx"?</LI>
<LI>If the test is to uncover a potential issue, does title contain the issue you are trying to uncover (eg. SQL Injection, Buffer Overflow)? </LI>
<LI>If the test is to verify correct implementation or design does the title contain what you are trying to verify (Input is properly validated for length, range, format, type)? </LI>
<LI>If the item is a MUST, meaning it is prevelant and high impact, is Priority = p1? </LI>
<LI>If the item is a SHOULD, meaning it has less impact or is only applicable in narrower circumstances, is Priority = p2? </LI>
<LI>If the item is a COULD, meaning it is nice to know about but isn't highly prevelant or impactful, is Priority = p3?</LI>
<LI>If this item will have cascading impact on application design, is Type = Design? </LI>
<LI>If this item should be followed just before deployment, is concerned with configuration details or runtime behavior, is Type = Deployment?</LI>
<LI>If this item is still in progress or not fully reviewed, is Status = Beta? </LI></UL>
<P>&nbsp;</P>]]></content>
</guidanceItem>